Sharing collections with external teams

ABSTRACT

The disclosed technology provides for sharing of collections between teams from external entities. The present technology allows administrators of an entity to manage what teams from their entity can be exposed outside of the entity and to manage how their entity is viewed by external partners. Sharing between teams provides benefits of easier sharing whereby it is not necessary to share a collection individually with all users of a team. It also provides a more logical sharing paradigm where collaboration is otherwise thought of between two partner entities and not specific employees of those entities. Sharing between teams allows an administrator to manage the user accounts associated with the team so that as team members come and go, all current team members will have access to projects in which the team is involved. Additionally, established teams can be configured to enjoy the full collaborative benefits of the content management system.

TECHNICAL FIELD

The present technology pertains to sharing collections of content items,and more specifically pertains to sharing collections of content itemswith teams from external partners.

BACKGROUND

There exists many services for collaborating on projects. Many suchservices allow sharing of content items or collections with individuals.Some services recognize the existence of teams within a commonorganization, and allow sharing of content items or collections byteams. However known services for collaborating on projects don't have amechanism to share content items or collections with defined teams fromentities external to the users.

For example, known services for collaborating on projects will allow afirst user to individually invite other users to collaborate on aproject. Some services will also allow a first user as a member of afirst entity (e.g., company or other organization) to invite a teamwithin the first entity to collaborate on the project. But modernservices for collaborating on projects won't allow a first user as amember of a first entity to invite a team from a second entity tocollaborate on a project. This is a serious shortcoming to knowncollaboration tools as collaboration amongst entities has long been acommon practice.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-recited and other advantages and features of the presenttechnology will become apparent by reference to specific implementationsillustrated in the appended drawings. A person of ordinary skill in theart will understand that these drawings only show some examples of thepresent technology and would not limit the scope of the presenttechnology to these examples. Furthermore, the skilled artisan willappreciate the principles of the present technology as described andexplained with additional specificity and detail through the use of theaccompanying drawings in which:

FIG. 1 shows an example of a content management system and clientdevices in accordance with some embodiments;

FIG. 2 shows an example of a content management system for sharingcollections between team in accordance with some embodiments;

FIG. 3 shows an example method for establishing relationships betweenexternal entities in accordance with some embodiments;

FIG. 4A, FIG. 4B, FIG. 4C show example entity management user interfacesin accordance with some embodiments;

FIG. 5 shows an example method for sharing a collection using acollection sharing interface in accordance with some embodiments;

FIG. 6A and FIG. 6B show example collection sharing interfaces inaccordance with some embodiments;

FIG. 7 shows an example method for displaying a partnership managementuser interface in accordance with some embodiments;

FIGS. 8A and 8B shows an example partnership management user interfacein accordance with some embodiments;

FIG. 9 shows an entity management user interface for removing a partnerin accordance with some embodiments; and

FIG. 10 shows an example of a system for implementing certain aspects ofthe present technology.

DETAILED DESCRIPTION

Various examples of the present technology are discussed in detailbelow. While specific implementations are discussed, it should beunderstood that this is done for illustration purposes only. A personskilled in the relevant art will recognize that other components andconfigurations may be used without parting from the spirit and scope ofthe present technology.

The disclosed technology addresses the need in the art for acollaboration service that can facilitate collaboration amongst teamsfrom diverse entities. Collaboration amongst teams in different entitieshas long been a common practice. For example, it is quite common for afirst entity to hire a contractor to develop a portion of a project.However modern collaboration tools do not permit or facilitate easysharing of a project amongst teams from diverse entities. While it ispossible using several different tools to invite individuals fromoutside entities to collaborate on content items or a collection, thesetools do not permit sharing with teams from outside entities.

This is less than ideal because often, as in the contractor use case, aproject is not necessarily limited to the individuals actively workingon content items—there may be managers and other team members involved.One limitation of the sharing with individuals paradigm and thecontractor example occurs when the individual to which a content item orcollection has been shared leaves their employment with the contractor.When this occurs the project does not end, but because sharing waslimited to individuals other members of the team at the contractor wouldbe left in the dark. It is more desirable to share the project with thecontractor entity or a team entity at the contractor. The presenttechnology provides for forming and managing teams and permittingsharing of collections with teams including teams external to the entitythat is sharing the collection.

In addition to providing a more logical way to share collections outsideof an entity, the present technology also allows administrators of anentity to manage how their entity is viewed by external partners. Forexample an entity may make use of contractors, and would like to allowthose contractors to collaborate with the entity's clients, but thatentity would prefer that the contractors appear as full members of theentity and not expose the subcontractor relationship. Additionally anentity may have a management structure that they wish or do not wish tobe exposed to their collaborators. The present technology permitsadministrators to configure teams within their entity to appear toexternal partners according to entity practices. These and otherbenefits will be described further herein.

In some embodiments the disclosed technology is deployed in the contextof a content management system having content item synchronizationcapabilities and collaboration features, among others. An example systemconfiguration 100 is shown in FIG. 1, which depicts content managementsystem 110 interacting with client device 150.

The present technology permits sharing of collections between teams fordifferent entities. Sharing between teams provides benefits of allowingan administrator to manage the user accounts associated with the team sothat as team members come and go, all current team members will haveaccess to projects in which the team is involved. Additionally,established teams can be configured to enjoy the full collaborativebenefits of content management system 110. For example, a prerequisiteto forming a team can be to identify team members and give team membersuser accounts in the content management system 110. Since each teammember has a user account, functions provided by the content managementsystem 110 such as seen state, revision histories, tagging, commentingon content items, etc. can be available to external partners, as well asthe team sharing the collection.

Accounts

Content management system 110 can store content items in associationwith accounts, as well as perform a variety of content item managementtasks, such as retrieve, modify, browse, and/or share the contentitem(s). Furthermore, content management system 110 can enable anaccount to access content item(s) from multiple client devices.

Content management system 110 supports a plurality of accounts. Anentity (user, group of users, company, etc.) can create an account withcontent management system, and account details can be stored in accountdatabase 140. Account database 140 can store profile information forregistered entities. In some cases, profile information for registeredentities includes a username and/or email address. Account database 140can include account management information, such as account type (e.g.various tiers of free or paid accounts), storage space allocated,storage space used, client devices 150 having a registered contentmanagement client application 152 resident thereon, security settings,personal configuration settings, etc.

Account database 140 can store groups of accounts associated with anentity. Groups/teams can have permissions based on group policies and/oraccess control lists, and members of the groups/teams can inherit thepermissions. For example, a marketing group can have access to one setof content items while an engineering group can have access to anotherset of content items. An administrator group can modify groups, modifyuser accounts, etc.

Content Item Storage

A feature of content management system 110 is the storage of contentitems, which can be stored in content storage 142. Content items can beany digital data such as documents, collaboration content items, textfiles, audio files, image files, video files, webpages, executablefiles, binary files, etc. A content item can also include collections orother mechanisms for grouping content items together with differentbehaviors, such as folders, zip files, playlists, albums, etc. Acollection can refer to a folder, or a plurality of content items thatare related or grouped by a common attribute. In some embodiments,content storage 142 is combined with other types of storage or databasesto handle specific functions. Content storage 142 can store contentitems, while metadata regarding the content items can be stored inmetadata database 146. Likewise, data regarding where a content item isstored in content storage 142 can be stored in content directory 144.Additionally, data regarding changes, access, etc. can be stored inserver file journal 148. Each of the various storages/databases such ascontent storage 142, content directory 144, server file journal 148, andmetadata database 146 can be comprised of more than one such storage ordatabase and can be distributed over many devices and locations. Otherconfigurations are also possible. For example, data from content storage142, content directory 144, server file journal 148, and/or metadatadatabase 146 may be combined into one or more content storages ordatabases or further segmented into additional content storages ordatabases. Thus, content management system 110 may include more or lessstorages and/or databases than shown in FIG. 1.

In some embodiments, content storage 142 is associated with at least onecontent management service 116, which includes software or otherprocessor executable instructions for managing the storage of contentitems including, but not limited to, receiving content items forstorage, preparing content items for storage, selecting a storagelocation for the content item, retrieving content items from storage,etc. In some embodiments, content management service 116 can divide acontent item into smaller chunks for storage at content storage 142. Thelocation of each chunk making up a content item can be recorded incontent directory 144. Content directory 144 can include a content entryfor each content item stored in content storage 142. The content entrycan be associated with a unique ID, which identifies a content item.

In some embodiments, the unique ID, which identifies a content item incontent directory 144, can be derived from a deterministic hashfunction. This method of deriving a unique ID for a content item canensure that content item duplicates are recognized as such since thedeterministic hash function will output the same identifier for everycopy of the same content item, but will output a different identifierfor a different content item. Using this methodology, content managementservice 116 can output a unique ID for each content item.

Content management service 116 can also designate or record a contentpath for a content item. The content path can include the name of thecontent item and/or folder hierarchy associated with the content item.For example, the content path can include a folder or path of folders inwhich the content item is stored in a local file system on a clientdevice. Content management service 116 can use the content path topresent the content items in the appropriate folder hierarchy, such as atree-like directory structure. While content items are stored in contentstorage 142 in blocks and may not be stored under a tree like directorystructure, such directory structure is a comfortable navigationstructure for users. Content management service 116 can define or recorda content path for a content item wherein the “root” node of a directorystructure can be a namespace for each account. Within the namespace canbe a directory structure defined by a user of an account and/or contentmanagement service 116. Content directory 144 can store the content pathfor each content item as part of a content entry.

In some embodiments the namespace can include additional namespaces thatappear in the directory structure as if they are stored within the rootnode. This can occur when an account has access to a shared collection.Shared collections can be assigned their own namespace within contentmanagement system 110. While shared collections are actually a root nodefor the shared collection, they are located subordinate to the useraccount namespace in the directory structure, and can appear as a folderwithin a folder for the user account. As addressed above, the directorystructure is merely a comfortable navigation structure for users, butdoes not correlate to storage locations of content items in contentstorage 142.

While the directory structure in which an account views content itemsdoes not correlate to storage locations at content management system110, the directory structure can correlate to storage locations onclient device 150 depending on the file system used by client device150.

As addressed above, a content entry in content directory 144 can alsoinclude the location of each chunk making up a content item. Morespecifically, the content entry can include content pointers thatidentify the location in content storage 142 of the chunks that make upthe content item.

In addition to a content path and content pointer, a content entry incontent directory 144 can also include a user account identifier thatidentifies the user account that has access to the content item and/or agroup identifier that identifies a group with access to the contentitem. In some embodiments, multiple user account identifiers can beassociated with a single content entry indicating that the content itemhas shared access by the multiple user accounts. In some embodiments,user account identifiers associated with a single content entry canspecify different permissions for the associated content item. In someembodiments, content directory 144 can describe a hierarchical structureof content items associated with a user account, the hierarchicalstructure being specific to the user account.

Content management service 116 can decrease the amount of storage spacerequired by identifying duplicate content items or duplicate blocks thatmake up a content item or versions of a content item. Instead of storingmultiple copies, content storage 142 can store a single copy of thecontent item or block of the content item and content directory 144 caninclude a pointer or other mechanism to link the duplicates to thesingle copy.

Content management service 116 can also store metadata describingcontent items, content item types, folders, file path, and/or therelationship of content items to various accounts, collections, orgroups in metadata database 146, in association with the unique ID ofthe content item.

Content management service 116 can also store a log of data regardingchanges, access, etc. in server file journal 148. Server file journal148 can include the unique ID of the content item and a description ofthe change or access action along with a time stamp or version numberand any other relevant data. Server file journal 148 can also includepointers to blocks affected by the change or content item access.Content management service can provide the ability to undo operations,by using a content item version control that tracks changes to contentitems, different versions of content items (including diverging versiontrees), and a change history that can be acquired from the server filejournal 148. The change history can include a set of changes that, whenapplied to the original content item version, produce the changedcontent item version.

Content Item Synchronization

Another feature of content management system 110 is synchronization ofcontent items with at least one client device 150. Client device(s) cantake different forms and have different capabilities. For example,client device 170 is a computing device having a local file systemaccessible by multiple applications resident thereon. Client device 172is a computing device wherein content items are only accessible to aspecific application or by permission given by the specific application,and the content items are stored either in an application specific spaceor in the cloud. Client device 174 is any client device accessingcontent management system 110 via a web browser and accessing contentitems via a web interface. While example client devices 170, 172, and174 are depicted in form factors such as a laptop, mobile device, or webbrowser, it should be understood that the descriptions thereof are notlimited to devices of these example form factors. For example a mobiledevice such as client 172 might have a local file system accessible bymultiple applications resident thereon, or client 172 might accesscontent management system 110 via a web browser. As such, the formfactor should not be considered limiting when considering client 150'scapabilities. One or more functions described herein with respect toclient device 150 may or may not be available on every client devicedepending on the specific capabilities of the device—the file accessmodel being one such capability.

In many embodiments, client devices are associated with an account ofcontent management system 110, but in some embodiments client devicescan access content using shared links and do not require an account.

As noted above, some client devices can access content management system110 using a web browser. However, client devices can also access contentmanagement system 110 using client application 152 stored and running onclient device 150. Client application 152 can include a content itemsynchronization service 156.

Content item synchronization service 156 can be in communication withcontent management service 116 to synchronize changes to content itemsbetween client device 150 and content management system 110.

Client device 150 can synchronize content with content management system110 via content synchronization service 156. The synchronization can beplatform agnostic. That is, content can be synchronized across multipleclient devices of varying type, capabilities, operating systems, etc.Content synchronization service 156 can synchronize any changes (new,deleted, modified, copied, or moved content items) to content items in adesignated location of a file system of client device 150.

Content items can be synchronized from client device 150 to contentmanagement system 110, and vice versa. In embodiments whereinsynchronization is from client device 150 to content management system110, a user can manipulate content items directly from the file systemof client device 150, while file system extension 153 (which can beintegrated with the local file system, or even the operating systemkernel) can intercept read, write, copy, move, delete commands relativeto content items in the designated location of the file system of clientdevice 150.

When file system extension 153 notices a write, move, copy, or deletecommand, it can notify content item synchronization service 156, whichcan synchronize the changes to content management system service 116. Insome embodiments, content item synchronization service 156 can performsome functions of content management system service 116 includingfunctions addressed above such as dividing the content item into blocks,hashing the content item to generate a unique identifier, etc. Contentsynchronization service 156 can index content within client storageindex 164 and save the result in storage index 164. Indexing can includecreating a unique identifier for each content item. In some embodiments,content synchronization service 156 creates this unique identifier byputting the data of the content item (e.g., excluding the filenameand/or other metadata) through a hash function; as addressed above,content management system can use a similar process to provideidentifiers to content on content management system 110. Contentsynchronization service 156 can use storage index 164 to facilitate thesynchronization of at least a portion of the content within clientstorage with content associated with a user account on contentmanagement system 110. For example, content synchronization service 156can compare storage index 164 with content management system 110 anddetect differences between content on client storage and contentassociated with a user account on content management system 110. Contentsynchronization service 156 can then attempt to reconcile differences byuploading, downloading, modifying, and deleting content on clientstorage as appropriate. Content management service 116 can store thechanged or new block for the content item and update server file journal148, metadata database 146, content directory 144, content storage 142,account database 140, etc. as appropriate.

When synchronizing from content management system 110 to client device150, a modification, addition, deletion, move of a content item recordedin server file journal 148 can trigger a notification to be sent toclient device 150 using notification service 116. When client device 150is informed of the change to server file journal 148, client device cancheck storage index 164 to determine if the time stamp of the changeoccurred since the last synchronization, or determine if the specificchange has been synchronized. When client device 150 determines that itis out of synchronization with content management system 110, contentitem synchronization service 156 requests content item blocks includingthe changes, and updates its local copy of the changed content items. Insome embodiments, notification service can query other services ordatabases of content management system 110 such as server file journal148 to gain more context for the notification, to determine if anotification can be batched with another notification or to supplement anotification

Sometimes client device 150 might not have a network connectionavailable. In this scenario, content item synchronization service 156can monitor the linked collection for content item changes and queuethose changes for later synchronization to content management system 110when a network connection is available. Similarly, a user can manuallystart, stop, pause, or resume synchronization with content managementsystem 110.

Content item synchronization service 156 can synchronize all contentassociated with a particular user account on content management system110. Alternatively, content item synchronization service 156 canselectively synchronize a portion of the content of the total contentassociated with the particular user account on content management system110. Selectively synchronizing only a portion of the content canpreserve space on client device 150 and save bandwidth.

In some embodiments, content item synchronization service 156selectively stores a portion of the content associated with theparticular user account and stores placeholder content items in clientstorage for the remainder portion of the content. For example, contentitem synchronization service 156 can store a placeholder content itemthat has the same filename, path, extension, metadata, of its respectivecomplete content item on content management system 110, but lacking thedata of the complete content item. The placeholder content item can be afew kilobytes or less in size while the respective complete content itemmight be significantly larger. After client device 150 attempts toaccess the content item, content item synchronization service 156 canretrieve the data of the content item from content management system 110and provide the complete content item to accessing client device 150.This approach can provide significant space and bandwidth savings whilestill providing full access to a user's content on content managementsystem 110.

Collaboration Features

Another feature of content management system 110 is to facilitatecollaboration between users. Collaboration features include content itemsharing, commenting on content items, co-working on content items,instant messaging, providing presence and seen state informationregarding content items, etc.

Sharing

Content management system 110 can manage sharing content via sharingservice 128. Sharing content by providing a link to the content caninclude making the content item accessible from any computing device innetwork communication with content management system 110. However, insome embodiments a link can be associated with access restrictionsenforced by content management system 110. Sharing content can alsoinclude linking content using sharing service 128 to share contentwithin content management system 110 with at least one additional useraccount (in addition to the original user account associated with thecontent item) so that each user account has access to the content item.The additional user account can gain access to the content by acceptingthe content, which will then be accessible through either web interfaceservice 124 or directly from within the directory structure associatedwith their account on client device 150. The sharing can be performed ina platform agnostic manner. That is, the content can be shared acrossmultiple client devices 150 of varying type, capabilities, operatingsystems, etc. The content can also be shared across varying types ofuser accounts.

To share a content item within content management system 110 sharingservice 128 can add a user account identifier to a content entry inaccess control list database 145 associated with the content item, thusgranting the added user account access to the content item. Sharingservice 128 can also remove user account identifiers from a contententry to restrict a user account's access to the content item. Sharingservice 128 can record content item identifiers, user accountidentifiers given access to a content item, and access levels in accesscontrol list database 145.

To share content items outside of content management system 110, sharingservice 128 can generate a custom network address, such as a uniformresource locator (URL), which allows any web browser to access thecontent item or collection in content management system 110 without anyauthentication. To accomplish this, sharing service 128 can includecontent identification data in the generated URL, which can later beused to properly identify and return the requested content item. Forexample, sharing service 128 can include the account identifier and thecontent path or a content item identifying code in the generated URL.Upon selection of the URL, the content identification data included inthe URL can be transmitted to content management system 110, which canuse the received content identification data to identify the appropriatecontent item and return the content item.

In addition to generating the URL, sharing service 128 can also beconfigured to record in access control list database 145 that a URL tothe content item has been created. In some embodiments, the contententry associated with a content item can include a URL flag indicatingwhether a URL to the content item has been created. For example, the URLflag can be a Boolean value initially set to 0 or false to indicate thata URL to the content item has not been created. Sharing service 128 canchange the value of the flag to 1 or true after generating a URL to thecontent item.

In some embodiments, sharing service 128 can associate a set ofpermissions to a URL for a content item. For example, if a user attemptsto access the content item via the URL, sharing service 128 can providea limited set of permissions for the content item. Examples of limitedpermissions include restrictions that the user cannot download thecontent item, save the content item, copy the content item, modify thecontent item, etc. In some embodiments, limited permissions includerestrictions that only permit a content item to be accessed from with aspecified domain, i.e., from within a corporate network domain, or byaccounts associated with a specified domain, e.g., accounts associatedwith a company account (e.g., @acme.com).

In some embodiments, sharing service 128 can also be configured todeactivate a generated URL. For example, each content entry can alsoinclude a URL active flag indicating whether the content should bereturned in response to a request from the generated URL. For example,sharing service 128 can only return a content item requested by agenerated link if the URL active flag is set to 1 or true. Thus, accessto a content item for which a URL has been generated can be easilyrestricted by changing the value of the URL active flag. This allows auser to restrict access to the shared content item without having tomove the content item or delete the generated URL. Likewise, sharingservice 128 can reactivate the URL by again changing the value of theURL active flag to 1 or true. A user can thus easily restore access tothe content item without the need to generate a new URL.

In some embodiments, content management system 110 can designate a URLfor uploading a content item. For example, a first user with a useraccount can request such a URL, provide the URL to a contributing userand the contributing user can upload a content item to the first user'suser account using the URL.

Presence and Seen State

In some embodiments, content management system can provide informationabout how users with which a content item is shared are interacting orhave interacted with the content item. In some embodiments, contentmanagement system 110 can report that a user with which a content itemis shared is currently viewing the content item. For example, clientcollaboration service 160 can notify notifications service 117 whenclient device 150 is accessing the content item. Notifications service117 can then notify all client devices of other users having access tothe same content item of the presence of the user of client device 150with respect to the content item.

In some embodiments, content management system 110 can report a historyof user interaction with a shared content item. Collaboration service126 can query data sources such as metadata database 146 and server filejournal 148 to determine that a user has saved the content item, that auser has yet to view the content item, etc., and disseminate this statusinformation using notification service 117 to other users so that theycan know who currently is or has viewed or modified the content item.

Collaboration service 126 can facilitate comments associated withcontent, even if a content item does not natively support commentingfunctionality. Such comments can be stored in metadata database 146.

Collaboration service 126 can originate and transmit notifications forusers. For example, a user can mention another user in a comment andcollaboration service 126 can send a notification to that user that hehas been mentioned in the comment. Various other content item events cantrigger notifications, including deleting a content item, sharing acontent item, etc.

Collaboration service 126 can provide a messaging platform whereby userscan send and receive instant messages, voice calls, emails, etc.

Collaboration Content Items

Collaboration service 126 can also provide an interactive content itemcollaboration platform whereby users can simultaneously createcollaboration content items, comment in the collaboration content items,and manage tasks within the collaboration content items. Collaborationcontent items can be files that users can create and edit using acollaboration content item editor, and can contain collaboration contentitem elements. Collaboration content item elements may include acollaboration content item identifier, one or more author identifiers,collaboration content item text, collaboration content item attributes,interaction information, comments, sharing users, etc. Collaborationcontent item elements can be stored as database entities, which allowsfor searching and retrieving the collaboration content items. Multipleusers may access, view, edit, and collaborate on collaboration contentitems at the same time or at different times. In some embodiments thiscan be managed by requiring two users access a content item through aweb interface and there they can work on the same copy of the contentitem at the same time.

Collaboration Companion Interface

In some embodiments client collaboration service 160 can provide anative application companion interface for the purpose of displayinginformation relevant to a content item being presented on client device150. In embodiments wherein a content item is accessed by a nativeapplication stored and executed on client device 150, where the contentitem is in a designated location of the file system of client device 150such that the content item is managed by content application 152, thenative application may not provide any native way to display the aboveaddressed collaboration data. In such embodiments, client collaborationservice 160 can detect that a user has opened a content item, and canprovide an overlay with additional information for the content item,such as collaboration data. For example, the additional information caninclude comments for the content item, status of the content item,activity of other users previously or currently viewing the contentitem. Such an overlay can warn a user that changes might be lost becauseanother user is currently editing the content item.

In some embodiments, one or more of the services or storages/databasesdiscussed above can be accessed using public or private applicationprogramming interfaces.

Certain software applications can access content storage 142 via an APIon behalf of a user. For example, a software package such as anapplication running on client device 150, can programmatically make APIcalls directly to content management system 110 when a user providesauthentication credentials, to read, write, create, delete, share, orotherwise manipulate content.

A user can view or manipulate content stored in a user account via a webinterface generated and served by web interface service 124. Forexample, the user can navigate in a web browser to a web addressprovided by content management system 110. Changes or updates to contentin the content storage 142 made through the web interface, such asuploading a new version of a content item, can be propagated back toother client devices associated with the user's account. For example,multiple client devices, each with their own client software, can beassociated with a single account and content items in the account can besynchronized between each of the multiple client devices.

Client device 150 can connect to content management system 110 on behalfof a user. A user can directly interact with client device 150, forexample when client device 150 is a desktop or laptop computer, phone,television, internet-of-things device, etc. Alternatively oradditionally, client device 150 can act on behalf of the user withoutthe user having physical access to client device 150, for example whenclient device 150 is a server.

Some features of client device 150 are enabled by an applicationinstalled on client device 150. In some embodiments, the application caninclude a content management system specific component. For example, thecontent management system specific component can be a stand-aloneapplication 152, one or more application plug-ins, and/or a browserextension. However, the user can also interact with content managementsystem 110 via a third-party application, such as a web browser, thatresides on client device 150 and is configured to communicate withcontent management system 110. In various implementations, theclient-side application 152 can present a user interface (UI) for a userto interact with content management system 110. For example, the usercan interact with the content management system 110 via file systemextension 153 integrated with the file system or via a webpage displayedusing a web browser application.

In some embodiments, client application 152 can be configured to manageand synchronize content for more than one account of content managementsystem 110. In such embodiments client application 152 can remain loggedinto multiple accounts and provide normal services for the multipleaccounts. In some embodiments, each account can appear as folder in afile system, and all content items within that folder can besynchronized with content management system 110. In some embodiments,client application 152 can include a selector to choose one of themultiple accounts to be the primary account or default account.

While content management system 110 is presented with specificcomponents, it should be understood by one skilled in the art, that thearchitectural configuration of system 100 is simply one possibleconfiguration and that other configurations with more or fewercomponents are possible. Further, a service can have more or lessfunctionality, even including functionality described as being withanother service. Moreover, features described herein with respect to anembodiment can be combined with features described with respect toanother embodiment.

While system 100 is presented with specific components, it should beunderstood by one skilled in the art, that the architecturalconfiguration of system 100 is simply one possible configuration andthat other configurations with more or fewer components are possible.

As addressed above the present technology provides for better managementof teams within an entity and provides for sharing of collectionsbetween teams from diverse entities. FIG. 2 illustrates additionaldetails of content management system 110 that are useful in the contextof the team collaboration technology described herein.

As used herein, different entities refer to companies or otherorganizations that, outside of their collaboration on projects, areseparate entities. They will often have their own defined legalformations. The entities will also not share an information technologyinfrastructure other that perhaps separately having relationships withcommon vendors. User accounts of one entity are not transferrable toanother entity, and user accounts of one entity do not provideprivileges with respect to another entity. In some embodiments, entitiescan be companies.

FIG. 2 illustrates an extension of sharing service 128, team managementservice 180. Team management service 180 can facilitate the creation ofteams and storing information regarding teams in teams database 182.Team management service 180 can also facilitate collaborationrelationships between teams, whether those teams are within a commonentity or are within diverse entities, and store relationships betweenteams in team relationship database 184.

Teams database 182 can store data defining an entity or team and itsmembers, and in some embodiments team database 182 can store teamspecific configuration data. An administrator of an entity can interactwith team management service 180 to create a profile for the entity. Bydefault, the entity can be associated with all teams or individualswithin the entity. The administrator for the entity can create otherteams within the entity and can nest teams within teams. In someembodiments an administrator for the entity may need to invite membersto a team.

Teams database 182 can identify entities and teams by identifiers, andstore user account identifiers for members of the respective team orrespective entity. For example, as illustrated in FIG. 2, a firstentity, “entity_ID_1” can include a plurality of users identified bytheir user account IDs. This first entity, might be a small entity andnot require further division into teams. In contrast, a second entity“entity_ID_2” can be a larger entity and can be made up of users, andteams. For example, the second entity can be made up of team_ID_1,team_ID_2, and userID₉ As such, entities can be defined by teams andindividual users.

Teams database 182 also defines teams such as team_ID_1, team_ID_2. Bothteams consist of a plurality of users identified by their user IDs.

An administrator for the entity can keep the entity reflected in teamsdatabase 182 up to date by editing the teams and individuals associatedwith the entity as needed. Likewise, managers of teams or entityadministrators can also manage the user accounts associated withindividual teams and keep them up to day in team database 182.

Teams database 182 can also record configuration data for teams.Configuration parameters may include parameters that may expose or hideteams from the entity to external partners, hide individual members of ateam, display or hide roles of such members, visibility ofsubcontractors, and visibility of team structures, etc. Configurationparameters can also influence the how the behavior of the team, in thecontext of specific features of content management system 110, is viewedby partner teams. For example, content management system 110 providesseen state and edit histories, commenting, etc. In some embodiments, aconfiguration parameter can affect how this type of data is viewed byexternal entities. For example, rather than edit histories reflectingthe user accounts that provided the edits, a team can be configured sothat edit histories reflect that edits were made by the team rather thana specific team member. Other configurations are also possible.

Team relationship database 184 can define relationships between two ormore teams. In some embodiments the relationship between two or moreteams can be apparent from the members that make up the relationship.While in some embodiments the relationship between two or more teams maybe defined or edited by an administrator. FIG. 2 illustrates somedifferent types of relationships between a team and another party. Ateam-friend relationship is a relationship between a team and anindividual user. A team-team relationship is a relationship between twoteams. An alliance his relationship between three or more teams. Ateam-subcontractor relationship is a relationship between a team and asubcontractor. And an alliance-team relationship is a relationshipbetween alliance and another team. In some embodiments, the type ofrelationship can be used to determine an appropriate model or templatefor displaying relationship partners to other partners, e.g., as in thecase of a team-team relationship, where one of the teams in therelationship is itself a team-subcontractor relationship.

Each of the relationships can be assigned a unique ID.

FIG. 3 illustrates an example method of forming a relationship betweenentities. Team management service can present (202) an entity managementuser interface such as illustrated in FIG. 4A. An administrator of afirst entity can request (204) to add a second entity as a partner. Forexample, as illustrated in FIG. 4A, the entity management user interfaceincludes “add partner” button 306. The administrator of the first entitycan select this button to request (204) to add the second entity as apartner. Selection of “add partner” button 306 can cause team managementservice 180 to display the interface shown in FIG. 4B. The administratorof the first entity can type the name of the second entity in field 310.If the second entity is already in teams database 182 the second entitywill appear in a list of results 312. If the second entity is notpresent in teams database 182, the administrator of the first entity canprovide an email address of a team member of the second entity.

After requesting to add (204) a second entity as a partner, teammanagement service 180 can form (206) a relationship between the firstentity and the second entity by recording (208) the relationship betweenthe first entity and second entity. In some embodiments team managementservice 180 waits to receive a confirmation from the second entitybefore forming (206) a relationship between the first entity and secondentity.

In addition to presenting controls to add new partners, entitymanagement user interface illustrated in FIG. 4A also shows a “mypartners” tab 302 and a “suggested partners” tab 304. “My partners” tab302 includes entities 308 that already have a relationship with thefirst entity. FIG. 4C illustrates “suggested partners” tab 304. Thepartners 314 are entities where an individual(s) from that entityalready is collaborating with a person, team, or individual(s) from thefirst entity. In some embodiments suggested partners 314 are entitiesthat are already established in teams database 182, but do not yet havea relationship recorded in teams database 182.

FIG. 5 illustrates an example method for adding a team of an externalpartner to share a collection (while this description predominately tosharing collections the present technology can also be used to sharecontent items). The method begins when the user account associated withthe first entity interacts with client device 150 and requests todisplay (402) a collection sharing interface.

FIG. 6A and FIG. 6B illustrate example collection sharing interfaces.While these interfaces are configured to be displayed with local filesystem of client device 150, collection sharing interface could also bedisplayed in a web browser interacting with content management system110. In FIG. 6A the user account selects folder icon 440 representing acollection and brings up a contextual menu (in some embodimentscontextual menu is retrieved in response to a right-click on folder440). The user account selects share 442 from the contextual menu whichlaunches the interface illustrated in FIG. 6B.

As the user account interacts with selection area 444 in the interfaceillustrated in FIG. 6B, the interface can display (404) a list contactsincluding external partners to which the first entity has a relationshiprecorded in team relationship database 184, along with internalpartners, and other contacts of the user account. The user account canselect (406) an external partner with which to share the collection. InFIG. 6B user account has selected the design team from second entity“Company 7” and has given this team edit privileges 446 to collection440. Team management service 180 can record the team-team relationshipbetween the team to which the user accounts belongs, and the design teamfrom the external entity, Company 7, and provide (408) appropriateaccess rights to members of the design team the external entity.

In some embodiments the access rights to members of the design team ofthe external entity can be recorded in access control list 145.

The present technology provides significant conveniences when it comesto sharing collections. First, the collection can be shared directlywith the external team. A user account does not need to individuallyinvite each member of the external team to share the collection.Additionally, any user associated with a team can also be provided withthe features provided to the partner sharing the content item throughits subscription, so both teams can collaborate more completely thanmerely sharing content items. Furthermore, both teams can suffer lessdisruptions from changes in a team since sharing is a the team level,individual leaving a team do not affect the sharing between remainingmembers of the team.

As described above with respect to FIG. 3, user accounts withadministrator privileges are required to link partner entities together.However as described with respect to FIG. 5 any user account that hassufficient privileges to share the can invite teams from entities thatare already considered partners of the first entity.

In some embodiments, team management service 180 can identify the typeof relationship based on characteristics of the first team and thesecond team. For example when three or more teams are joined in arelationship, team management service 180 can identify this relationshipas an alliance. However, when there is ambiguity in the type ofrelationship that has been formed, in some embodiments, team managementservice 180 can select a default relationship until the administrator ofthe first team changes the identity of the relationship. For example,when two teams are joined in a relationship, team management service 180can label the relationship as a team-team relationship. However therelationship can be edited by an administrator of one of the teams ifthe more appropriate relationship is a team-subcontractor relationship.

In some embodiments only the administrator of the first entity is ableto edit the relationship between the first entity and the second entitysince the first entity is the one that has requested the relationshipwith the second entity. In such embodiments it can be assumed that thefirst entity is in control of that particular relationship.

Once teams are joined in a recorded relationship, an administrator canview details of sharing through the relationship using a partnershipmanagement user interface. FIG. 7 illustrates an example method fordisplaying certain information using a partnership management interface.FIG. 8A and FIG. 8B illustrate example partnership managementinterfaces.

An administrator of one of the entities involved in a relationship canrequest that team management service 180 present (502) partnershipmanagement user interface as illustrated in FIG. 8A. At step 504 anadministrator can request that partner teams are displayed (504) in thepartnership management user interface.

As illustrated in FIG. 8A, the partnership management user interfaceincludes multiple tabs including a tab for collections 520, contentitems 522, members 524, and groups 526. In FIG. 8A group tab 526 isdisplayed and shows teams exposed by the respective entities for thisrelationship. For example the first entity, Dropbox, has exposed teams530 including a marketing team, a design team, and a finance team. Whilethe second entity, Company 7, has exposed its design team 530.

In some embodiments, team management service 180 takes into accountrelationship attributes and other team configuration parameters whenpresenting the partnership management user interface. For example thesecond entity, Company 7, may itself be the result of a relationshipbetween a team at second entity and a subcontractor. In such an exampleteam management service 180 does not reveal the existence of thesubcontractor when displaying teams exposed by the second entity.

Other team configuration parameters may also exist such as, but notlimited to, parameters that may expose teams from the entity, hideindividual members of each team, display or hide roles of such members,visibility of subcontractors, and visibility of team structures.

In step 506 an administrator can request that the partnership managementuser interface display (506) collections shared with the externalpartner. FIG. 8B illustrates the partnership management user interfacewhen collections tab 520 has been selected. FIG. 8A shows severalcollections better shared between the first entity and the second entityand also shows which teams with which the collection is shared. Forexample collection 540 is shared between the design team of the secondentity, and the marketing and design teams of the first entity.

As illustrated in FIG. 9, at the end of the normal lifecycle of thecollaboration an administrator can interact with entity management userinterface to select an entity 604 and remove the entity using the removebutton 602. This will end any relationship between teams of the firstentity and the second entity.

FIG. 10 shows an example of computing system 700. Computing system 700can be for example a computing system of client device 150, or contentmanagement system 110. While these devices have some components incommon, such as those illustrated in computing system 700, it should beappreciated that each of payment client device 150, or contentmanagement system 110 are specialized devices configured for theirspecific purposes.

In computing system 700 the components of the system are incommunication with each other using connection 705. Connection 705 canbe a physical connection via a bus, or a direct connection intoprocessor 710, such as in a chipset architecture. Connection 705 canalso be a virtual connection, networked connection, or logicalconnection.

In some embodiments computing system 700 is a distributed system inwhich the functions described in this disclosure can be distributedwithin a datacenter, multiple datacenters, a peer network, etc. In someembodiments, one or more of the described system components representsmany such components each performing some or all of the function forwhich the component is described. In some embodiments, the componentscan be physical or virtual devices.

Example system 700 includes at least one processing unit (CPU orprocessor) 710 and connection 705 that couples various system componentsincluding system memory 715, such as read only memory (ROM) and randomaccess memory (RAM) to processor 710. Computing system 700 can include acache of high-speed memory connected directly with, in close proximityto, or integrated as part of processor 710.

Processor 710 can include any general purpose processor and a hardwareservice or software service, such as services 732, 734, and 736 storedin storage device 730, configured to control processor 710 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. Processor 710 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction, computing system 700 includes an inputdevice 745, which can represent any number of input mechanisms, such asa microphone for speech, a touch-sensitive screen for gesture orgraphical input, keyboard, mouse, motion input, speech, etc. Computingsystem 700 can also include output device 735, which can be one or moreof a number of output mechanisms known to those of skill in the art. Insome instances, multimodal systems can enable a user to provide multipletypes of input/output to communicate with computing system 700.Computing system 700 can include communications interface 740, which cangenerally govern and manage the user input and system output. There isno restriction on operating on any particular hardware arrangement andtherefore the basic features here may easily be substituted for improvedhardware or firmware arrangements as they are developed.

Storage device 730 can be a non-volatile memory device and can be a harddisk or other types of computer readable media which can store data thatare accessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs), read only memory (ROM), and/or somecombination of these devices.

The storage device 730 can include software services, servers, services,etc., that when the code that defines such software is executed by theprocessor 710, it causes the system to perform a function. In someembodiments, a hardware service that performs a particular function caninclude the software component stored in a computer-readable medium inconnection with the necessary hardware components, such as processor710, connection 705, output device 735, etc., to carry out the function.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Any of the steps, operations, functions, or processes described hereinmay be performed or implemented by a combination of hardware andsoftware services or services, alone or in combination with otherdevices. In some embodiments, a service can be software that resides inmemory of a client device and/or one or more servers of a contentmanagement system and perform one or more functions when a processorexecutes the software associated with the service. In some embodiments,a service is a program, or a collection of programs that carry out aspecific function. In some embodiments, a service can be considered aserver. The memory can be a non-transitory computer-readable medium.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, solid state memory devices, flash memory, USB devices providedwith non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include servers,laptops, smart phones, small form factor personal computers, personaldigital assistants, and so on. Functionality described herein also canbe embodied in peripherals or add-in cards. Such functionality can alsobe implemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

What is claimed is:
 1. A system comprising: at least one processor; afirst data structure defining a first team from a first entity and itsmembers, and a second team from a second entity and its members, thefirst entity and second entity being external from each other; a teammanagement service including processor executable instructions to causethe at least one processor to receive an input from an administratoraccount of the first team from the first entity requesting to create arelationship with the second team from the second entity; and a seconddata structure storing the relationship between the first team and thesecond team.
 2. The system of claim 1, wherein the team managementservice includes instructions to receive an input from the administratoraccount to configure the first team including instructions to inviteuser accounts within the first entity to be members of the first team,wherein the user accounts are stored in the first data structuredefining the first team from the first entity.
 3. The system of claim 1,wherein the team management service includes instructions to receive aninput from a member of the first team from the first entity to share acollection with the second team from the second entity.
 4. The system ofclaim 1, wherein the team management service includes instructions toreceive an input from the administrator account of the first entity tocreate a relationship with the second entity; and after the teammanagement service receives confirmation from a administrator account ofthe second entity, making teams of the second entity, including thesecond team, visible to the first team.
 5. The system of claim 3,wherein the second team appears in a contacts list of the member of thefirst team due to the relationship between the first team and the secondteam.
 6. The system of claim 4, wherein the teams visible to the firstentity were selected be the administrator of the second entity to beexposed to the first entity.
 7. The system of claim 6, wherein the teammanagement service includes instructions to display a partnership pagethat displays to an administrator of the first entity teams from thefirst entity exposed to the second entity and teams from the secondentity exposed to the first entity.
 8. The system of claim 1, whereinthe team management service includes instructions to display apartnership shared collection page showing teams from each entitysharing the shared collection(s).
 9. The system of claim 7, wherein thesecond data structure stores configuration parameters for the secondteam set by the administrator of the second entity, the configurationparameters identifying at least one of exposed teams, visibility ofsubcontractors, visibility of members of teams, visibility of teamstructures, and visibility of roles of team members.
 10. The system ofclaim 1, wherein the instructions to define a relationship between thefirst team from the first entity and the second team from the secondentity includes instructions to define the second entity as asubcontractor.
 11. The system of claim 1, wherein the team managementservice includes instructions to cause the at least one processor toreceive instructions from the administrator of the first team to createa relationship with a third team, wherein the second entity that is thesubcontractor is transparent to the members of the third team andthereby the members of the subcontractor appear as members of the firstteam.
 12. A non-transitory computer readable medium comprisinginstructions stored thereon, the instructions effective to cause atleast one processor to: define a first team from a first entity and itsmembers, and a second team from a second entity and its members, thefirst entity and second entity being external from each other; receivean input from an administrator account of the first team from the firstentity requesting to create a relationship with the second team from thesecond entity; and store the relationship between the first team and thesecond team.
 13. The non-transitory computer readable medium of claim12, wherein the instructions are effective cause the at least oneprocessor to receive an input from a member of the first team from thefirst entity to share a collection with the second team from the secondentity.
 14. The non-transitory computer readable medium of claim 12,wherein the instructions are effective cause the at least one processorto receive an input from the administrator account of the first entityto create a relationship with the second entity; and after the teammanagement service receives confirmation from a administrator account ofthe second entity, making teams of the second entity, including thesecond team, visible to the first team.
 15. The non-transitory computerreadable medium of claim 13, wherein the second team appears in acontacts list of the member of the first team due to the relationshipbetween the first team and the second team.
 16. The non-transitorycomputer readable medium of claim 12, wherein the instructions areeffective cause the at least one processor to display a partnershipshared collection page showing teams from each entity sharing the sharedcollection(s).
 17. The non-transitory computer readable medium of claim12, wherein the instructions are effective cause the at least oneprocessor to receive instructions from the administrator of the firstteam to create a relationship with a third team, wherein the secondentity that is the subcontractor is transparent to the members of thethird team and thereby the members of the subcontractor appear asmembers of the first team.
 18. A method comprising: defining a firstteam from a first entity and its members, and a second team from asecond entity and its members, the first entity and second entity beingexternal from each other; receiving an input from an administratoraccount of the first team from the first entity requesting to create arelationship with the second team from the second entity; and storingthe relationship between the first team and the second team.
 19. Themethod of claim 18, comprising: receiving an input from theadministrator account of the first entity to create a relationship withthe second entity; and after the team management service receivesconfirmation from an administrator account of the second entity, makingteams of the second entity, including the second team, visible to thefirst team.
 20. The method of claim 18, comprising: receivinginstructions from the administrator of the first team to create arelationship with a third team, wherein the second entity that is thesubcontractor is transparent to the members of the third team andthereby the members of the subcontractor appear as members of the firstteam.